High Profile Systems Illustrating Contradistinctive Aspects of Systems Engineering

AbstractMany modern systems have a high degree of dependence on embedded software in order to perform their required functions. Some examples include transportation systems, hand-held devices, and medical equipment, among others. In designing their products, systems engineers typically take a top-down, process-oriented approach, decomposing a complex system into simpler, easier to manage, subsystems; the system requirements can then be allocated and flowed down as necessary to the appropriate subsystems. Software engineers take a more bottom-up, object-oriented approach, using simple building blocks to create a more complex system, and enhancing their existing blocks with new ones where necessary.In many cases, both techniques must be employed together in order to design a successful system. Although it may have been acceptable in the past for simpler systems to view software as a separate subsystem with a fixed set of requirements, greater complexity of modern systems requires a corresponding improvement in working methodology. With the software playing an increasingly pivotal role, systems engineers must become much more familiar with the architecture of the software than previously; Likewise, software engineers need a systems-level view to understand which aspects of the design could be volatile due to new stakeholders (bringing with them new requirements), technology upgrades, and the changing world in general.Systems whose success or failure play out in the public arena provide a rare opportunity to study the factors that contribute to their outcome. Using two such systems, the Denver International Airport baggage handling system and the Apple iPad, this paper will study some best practices that can lead to project success or failure, and show the importance of a rigorous capture and flow down to both hardware and software of the requirements that must be correct from the start, as well as of designing an architecture that can accommodate the inevitable changes to a system.Designing extensible systems with a tolerance for future changes is a key factor in modern complex systems. The baggage handling system failed in part because of a failure to appreciate the central role of software and an apparent lack of a suitable strategy for handling requirement changes. Methods for creating software which is resilient to change have been well studied; however what may be somewhat lacking even to the present day is a broader education of the existing body of knowledge, and how to integrate it with systems engineering methods.The iPad succeeded where many of its predecessors had failed by a successful application of traditional systems engineering techniques and correctly implementing the hardware elements. Coming from companies with experience in software development, the system extensibility was not an issue in this case. However, the designers of the earlier systems seemingly failed to understand the actual market needs, failed to develop a corresponding set of requirements to meet those needs, and failed to translate those requirements into an integrated hardware/software solution

1 Requirement Elicitation and Validation by Prototyping and Demonstrators User Interface Development in the Oil- and Gas Industry

Copyright © 2010 by Jan Magnus Røkke Incomplete or misinterpreted requirements are a significant source of customer and user dissatisfaction in development of software user interfaces. In these systems, where consideration of the human factor is a vital part of the development, the undertaking of understanding the real needs of the user must not be underestimated. Unfortunately, there are often organizational boundaries which restrict or limit the developer’s opportunities to communicate with the customer and stakeholders. The result is often a weak link between the stakeholder needs, system requirements and the realization of the user interface system. This paper addresses how an approach to requirements engineering based on a combination of rapid prototyping and demonstrator sessions can be used to elicit requirements and obtain early feedback and acceptance from system stakeholders. The method was conducted on a user interface development project for gas turbine driven generator- and compressor packages in operation at offshore oil-rigs. Stakeholders were presented with module prototypes with a varying degree of dynamics, simulation and interaction based on the stage of the development. Together with rationale based questioning, the demonstrator sessions provided a context for constructive discussions and feedback. The developers returned with a better understanding of the rationale for stakeholder need and clarification of misinterpreted or poorly defined requirements. This enabled us to create an application better aligned with customer and user needs and a minimal amount of rework and updates after system deployment

ScienceDirect

Abstract In an effort to explore the relationship between the disciplines of systems engineering and software engineering, professionals from academia, industry, and government gathered for a workshop to deliberate on the current state, to acknowledge areas of inter-dependence, to identify relevant challenges, and to propose recommendations for addressing those challenges with respect to four topical areas: 1) Development Approaches, 2) Technical, 3) People, and 4) Education. This paper presents the deliberations and recommendations that emerged from that workshop, and the proposed project to be launched

The Evolution of Software and Its Impact on Complex System Design in Robotic Spacecraft Embedded Systems

AbstractThe growth in computer hardware performance, coupled with reduced energy requirements, has led to a rapid expansion of the resources available to software systems, driving them towards greater logical abstraction, flexibility, and complexity. This shift in focus from compacting functionality into a limited field towards developing layered, multi-state architectures in a grand field has both driven and been driven by the history of embedded processor design in the robotic spacecraft industry.The combinatorial growth of interprocess conditions is accompanied by benefits (concurrent development, situational autonomy, and evolution of goals) and drawbacks (late integration, non-deterministic interactions, and multifaceted anomalies) in achieving mission success, as illustrated by the case of the Mars Reconnaissance Orbiter. Approaches to optimizing the benefits while mitigating the drawbacks have taken the shape of the formalization of requirements, modular design practices, extensive system simulation, and spacecraft data trend analysis. The growth of hardware capability and software complexity can be expected to continue, with future directions including stackable commodity subsystems, computer-generated algorithms, runtime reconfigurable processors, and greater autonomy